home *** CD-ROM | disk | FTP | other *** search
- Path: keats.ugrad.cs.ubc.ca!not-for-mail
- From: c2a192@ugrad.cs.ubc.ca (Kazimir Kylheku)
- Newsgroups: comp.lang.ada,comp.lang.c,comp.lang.c++,comp.edu
- Subject: Re: ANSI C and POSIX (was Re: C/C++ knocks the crap out of Ada)
- Date: 10 Apr 1996 09:20:16 -0700
- Organization: Computer Science, University of B.C., Vancouver, B.C., Canada
- Message-ID: <4kgn40INN7g3@keats.ugrad.cs.ubc.ca>
- References: <JSA.96Feb16135027@organon.com> <dewar.829096975@schonberg> <4kf8k1INN68b@keats.ugrad.cs.ubc.ca> <dewar.829136049@schonberg>
- NNTP-Posting-Host: keats.ugrad.cs.ubc.ca
-
- In article <dewar.829136049@schonberg>, Robert Dewar <dewar@cs.nyu.edu> wrote:
- >Kazimir said
- >
- >"BTW, I checked the Ada POSIX standard too, but that reads like a VCR manual
- >from 1984. ;) heh"
- >
- >Actually, the Ada spec for the corresponding function is absolutely clear.
- >This is because the strong typing of Ada leaves no doubt as to the
- >semantics of exceeding the buffer size, and the called routine knows
- >the length of the buffer.
-
- It does! I was just kidding to be a pest! :)
-
- Do you think that the extra detail in the corresponding Ada function has any
- influence on how the ambiguities in the C function ought to be resolved?
- --
-
-